Organize skills with expo-* and eas-*#98
Merged
Merged
Conversation
Contributor
|
i feel building-native-ui is too large and not making sense map to expo-router directly. for instance, the maybe wait #99 to land first so we would be have clear expo-router skill then |
Prefix every skill with expo-* (framework/OSS) or eas-* (paid EAS service), and prefix each description with "Framework (OSS)." or "EAS service (paid)." so the free/paid boundary is visible in the always-loaded metadata and /expo- / /eas- discovery works. Renames to established product names: - building-native-ui (visual guide) -> expo-native-ui; navigation stays in the expo-router skill, matching the #99 split - native-data-fetching -> expo-data-fetching - use-dom -> expo-dom - web-to-native -> expo-web-to-native - add-app-clip -> expo-app-clip - upgrading-expo -> expo-upgrade - expo-observe -> eas-observe - expo-cicd-workflows -> eas-workflows - expo-deployment -> eas-app-stores (web deploy split into eas-hosting) - expo-api-routes -> eas-hosting Add CONTRIBUTING.md with documented patterns, CI checks for skill limits and plugin version bump, and bump the expo plugin to 1.7.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
davidmokos
approved these changes
Jul 7, 2026
davidmokos
left a comment
davidmokos
left a comment
Contributor
There was a problem hiding this comment.
I think the new structure is really good. I think some skills are still a bit too long but we should cover that in follow-up PRs
Contributor
|
late review but i do think we may need some further rename. e.g. expo-native-ui vs expo-ui feels unclear. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
We're adding many skills and our naming conventions and patterns have started to sprawl.
This PR makes some changes to organize them:
expo-*oreas-*. This helps discovery since you can type/expo-and then you'll see all related skills. Also creates a clear boundary btw free/paid.Framework (OSS)orEAS service (paid).Fixes ENG-23102
Breaking changes
There are no aliases for the old names for skills cli installations. So anyone who has installed
/building-native-uiwill no longer get updates. I don't think there's a way around this.Test plan
Please look at the skils and make sure they seem reasonable. Let me know if there are naming conventions/etc that you think we should change.
The new README is probably the best place to start: https://github.com/expo/skills/blob/bd295c4c5038247d6991aeac1e2d438118df62d1/README.md